Skip to content

docs: prepare Every Code branch release cutover#101

Merged
cbusillo merged 1 commit into
local/cbusillo-overlayfrom
feat/default-branch-release-identity
May 24, 2026
Merged

docs: prepare Every Code branch release cutover#101
cbusillo merged 1 commit into
local/cbusillo-overlayfrom
feat/default-branch-release-identity

Conversation

@cbusillo
Copy link
Copy Markdown
Owner

Summary

  • Document the Plan Every Code default branch and release identity #87 branch cutover blocker: origin/main already exists and diverges from local/cbusillo-overlay, so the remote branch move needs an explicit source-of-truth/admin decision
  • Add cutover-ready product commands: just local-upstream-import and just local-product-health, keeping legacy aliases intact
  • Prepare releases for the permanent every-code-v* tag prefix while preserving legacy overlay-v* history for release notes and triggers
  • Update repo metadata to distinguish current vs planned product branches without pretending GitHub has already switched

Validation

  • jq empty .github/github.json
  • Ruby YAML parse for .github/workflows/binary-release.yml
  • bash -n scripts/local/fork-health.sh scripts/local/generate-overlay-release-notes.sh scripts/local/update-overlay-from-upstream.sh
  • just --list | rg "local-(upstream-import|product-health|overlay-update|fork-health)"
  • Generated sample release notes with every-code-v0.6.98.1
  • ./build-fast.sh

Blocker intentionally left for #87

Actual GitHub default-branch cutover is not performed in this PR because origin/main already exists at ee5fd6dd9c, origin/local/cbusillo-overlay is at 89d88f62e5, and they diverge heavily. The next step is an explicit admin/source-of-truth decision to make main point at the current product branch, transfer branch protection, update the GitHub default branch, and only then retire or redirect the old branch.

Refs #87
Parent #85

@cbusillo cbusillo merged commit 14f29ff into local/cbusillo-overlay May 24, 2026
1 check passed
@cbusillo cbusillo deleted the feat/default-branch-release-identity branch May 24, 2026 04:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant